Governance and control
Invite colleagues with the access they need
A new colleague should be able to find the screens and content needed for their work as soon as they join the signage site. Preparing access before sending an invitation avoids a second round of assignments after acceptance—and avoids granting broad access just to get someone started.

This matters when an office is about to open, a department gains a local administrator, or a support colleague needs an agreed scope in an existing deployment. Give each person their own invitation rather than sharing or handing over an account, so responsibility remains clear.
Decide what the person will do and where
For a new location, first prepare its screens, local channel, media, and other required content resources. The location's screen folder can supply the intended Channels & layout, active time, other settings, and group access. Channels and layout are inherited or overridden together; other settings can have separate overrides. Its group connects the team to the resources they need.
Then choose the person's user profile. The profile defines their access type and allowed actions; resource assignments determine what a Group Access user can reach. Review these decisions together:
| Decision | What to check |
|---|---|
| Profile | Does it allow the person's tasks, with the appropriate access type? |
| Group memberships | Do they give access to the location and any shared resources needed? |
| Direct resource access | Are any exceptions intentional and still necessary? |
Membership of several groups combines access, and direct grants can add more. A resource assignment does not provide an action missing from the profile. Conversely, group scoping does not limit the reach of someone with Site Access. Roles and permissions explains how these decisions work together.
Administrators can grant only what their own administrative scope allows. Agree the intended responsibilities with the person being invited and the people responsible for the site before making the assignments.
Send the invitation with the working area prepared
Inviting users needs the Invite permission under Users in your user profile. The invitation's User details lets you select the profile, groups, and permitted direct access before sending. Confirm the email address the person will use, and check the Users list for an existing or pending user before creating another invitation. Invite a user gives the exact steps.
The recipient can accept or decline through the invitation link. Acceptance joins them with the assigned access. While the invitation is Pending, someone with user-edit access can still review or change that setup, so an office rollout need not wait for everyone to accept before preparing their working areas.
The Users area supports following up on invitations and managing existing accounts, including editing, exporting, and removing site users. A missed email can be handled by resending a pending invitation rather than starting another user request.
Check the result after acceptance
Verify both sides of the intended scope: the colleague can do their work, and unrelated resources remain inaccessible. A department administrator and a content contributor may use the same local resources but need different actions. Manage users and groups explains how to edit assignments and group resources.
A user with Site Access and the Assume identity permission can use Assume identity after an eligible user accepts to inspect their access. It is not available to Group Access users, and the target must belong to only one site. Review Assuming a user's identity before using this check.
Revisit access when responsibilities change
The invitation is the start of the arrangement, not its last review. When someone changes team, check their profile, all memberships, and direct grants again. Removing one group may leave access supplied through another route.
Keeping those assignments tied to responsibility makes access questions easier to answer as more people join. Let local teams publish within their own areas places this individual onboarding in the wider central-and-local publishing model.